Domain TRANSIT Request
Function
This request is used to place a domain in the administration of DENIC (TRANSIT). The RegAcc administering the domain up to that point in time will no longer have access to it.
Requirements
TRANSIT requests can be submitted only for domains of the requestor's own RegAcc. The domain must not have the status "failed".
Features
- When a domain is returned to DENIC, the AuthInfo1 which was stored with DENIC by the administering RegAcc becomes invalid and is deleted. The RegAcc placing the request is informed accordingly in the request acknowledgement. A possibly existing AuthInfo2 is not affected by the TRANSIT request.
- TRANSIT becomes impossible as soon as a domain has the status "failed".
- A TRANSIT request removes an existing General Request / Abuse Contact.
Verification
-
The verification period is lifted if the TRANSIT letter could be delivered (the letter does not come back to DENIC and the code in the letter was used).
-
The TRANSIT deadlines apply.
-
After a move out of TRANSIT, a new risk assessment is carried out as part of the provider change.
Request Parameters
A request comprises the parameters described below:
| K/V Keyword | XML Namespace and Element | Occurrence min - max |
Type / Length | Value Range | Description |
|---|---|---|---|---|---|
| Action | domain:transit | 1 | enumeration | transit-erule | This is the request type. |
| Version | - | 1 | enumeration | version-erule | This is the version. The keyword is only relevant for requests in the key/value format. |
| Domain | domain:handle | 1 | token 4 - 66 |
domain-rule | This is the name of the domain. |
| Disconnect | "disconnect" attribute for the " domain:transit " element | 0 - 1 | enumeration | boolean-erule | true = The prior name server entries will be replaced by an NS-Entry that makes reference to a DENIC webpage. false = The previous nameserver entries remain. |
| CtId | ctid | 0 - 1 | token 3 - 64 |
Any visible Unicode character (according to Unicode version 3.1) | This is the unique transaction ID which is issued by the client. |
Common Mistakes
The domain stated in the request does not exist.
One of the keywords stated in the request is invalid (e.g. deconnect instead of disconnect); the domain remains connected.